Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce the default verbosity of JS library error messages #8339

Merged
merged 2 commits into from
Mar 26, 2019

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Mar 24, 2019

Currently the entire library is printed which makes seeing the
actual error very difficult. Normally the filename and line number
should be sufficient and we can put the rest of it befind VERBOSE=1.

@sbc100 sbc100 requested a review from kripken March 24, 2019 02:23
Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm with those fixes.

error('failure to execute js library "' + filename + '": ' + details + '\npreprocessed source (you can run a js engine on this to get a clearer error message sometimes):\n=============\n' + processed + '\n=============\n');
error('failure to execute js library "' + filename + '": ' + details);
if (VERBOSE)
error('preprocessed source (you can run a js engine on this to get a clearer error message sometimes):\n=============\n' + processed + '\n=============');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

{, } if if/else bodies are on another line, like here and later down.

Currently the entire library is printed which makes seeing the
actual error very difficult.  Normally the filename and line number
should be sufficient and we can put the rest of it befind VERBOSE=1.
@sbc100 sbc100 merged commit 4840157 into incoming Mar 26, 2019
VirtualTim pushed a commit to VirtualTim/emscripten that referenced this pull request May 21, 2019
…-core#8339)

Currently the entire library is printed which makes seeing the
actual error very difficult.  Normally the filename and line number
should be sufficient and we can put the rest of it befind VERBOSE=1.
VirtualTim added a commit to VirtualTim/emscripten that referenced this pull request May 23, 2019
VirtualTim added a commit to VirtualTim/emscripten that referenced this pull request May 23, 2019
@sbc100 sbc100 deleted the cleaner_library_error branch August 19, 2019 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants